Security marketplace with provider verification and reporting

ABSTRACT

A system for generating and completing a security task is provided. A security task may be generated by the system based on a security task request. A security task acceptance for the security task may be received at the system. The system may validate the security task acceptance for the security task. The system may transmit a security task acceptance notification in response to validating the security task acceptance. The system may verify an identity of a security provider and generate a report associated with the security provider.

FIELD OF THE INVENTION

Embodiments of the present invention relate to a security marketplacehaving security provider verification and reporting.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter of the present disclosure is particularly pointed outand distinctly claimed in the concluding portion of the specification. Amore complete understanding of the present disclosure, however, may bestbe obtained by referring to the detailed description and claims whenconsidered in connection with the following illustrative figures. In thefollowing figures, like reference numbers refer to similar elements andsteps throughout the figures.

FIG. 1A is a block diagram illustrating system components of a securitymarketplace, in accordance with various embodiments;

FIG. 1B is a block diagram illustrating system components of a securitymarketplace into secondary security provider devices, in accordance withvarious embodiments;

FIG. 2A is a block diagram of an exemplary security consumer device foruse with a security marketplace, in accordance with various embodiments;

FIG. 2B is a block diagram of an exemplary security provider device foruse with a security marketplace, in accordance with various embodiments;

FIG. 2C is a block diagram of an exemplary third party system for usewith a security marketplace, in accordance with various embodiments;

FIG. 3 is a block diagram of an exemplary security marketplace, inaccordance with various embodiments;

FIG. 4 illustrates a process flow for a method of registering a securityconsumer for a security marketplace, in accordance with variousembodiments;

FIG. 5 illustrates a process flow for a method of registering a securityprovider for a security marketplace, in accordance with variousembodiments;

FIG. 6 illustrates a process flow for a method of generating a securitytask, in accordance with various embodiments;

FIG. 7 illustrates a process flow for a method of completing a securitytask, in accordance with various embodiments; and

FIG. 8 illustrates a process flow for a method of generating a securityprovider task report, in accordance with various embodiments;

FIG. 9A illustrates a process flow for a method for consumer activationof a security provider device, in accordance with various embodiments;

FIG. 9B illustrates a process flow for a method for task activation of asecurity provider device, in accordance with various embodiments; and

FIG. 10 is a block diagram illustrating components of a computer-basedsystem, in accordance with various embodiments.

Elements and steps in the figures are illustrated for simplicity andclarity and have not necessarily been rendered according to anyparticular sequence. For example, steps that may be performedconcurrently or in different order are illustrated in the figures tohelp to improve understanding of embodiments of the present disclosure.

DETAILED DESCRIPTION

The detailed description of various embodiments refers to theaccompanying drawings, which show various embodiments by way ofillustration. While these various embodiments are described insufficient detail to enable those skilled in the art to practice thedisclosure, it should be understood that other embodiments may berealized, and that logical and physical changes may be made withoutdeparting from the spirit and scope of the disclosure. Thus, thedetailed description is presented for purposes of illustration only andnot of limitation. For example, the steps recited in any of the methodor process descriptions may be executed in any order and are not limitedto the order presented. Moreover, any of the functions or steps may beoutsourced to or performed by one or more third parties. Furthermore,any reference to singular includes plural embodiments, and any referenceto more than one component may include a singular embodiment.

The systems, methods, and computer readable mediums (collectively, the“system”) described herein provide a security marketplace to enablecommunications between two or more of security consumers, securityproviders, and third party systems. The security marketplace may beconfigured to support the generation and completion of security tasks.For example, a security consumer may desire to have a security providercomplete a security task. The security marketplace may facilitate thegeneration and tracking of the security task, the transmission of thesecurity task, completion of the security task, payment for thecompletion of the security task, and/or reporting of the security taskfor the security provider, as discussed further herein. The securitymarketplace may communicate with one or more third party systems toprocess payments for the security task, verify the identity ofconsumers, verify the identity of providers, verify task policiesproviders are subject to, and/or transmit security provider taskreports, as discussed further herein.

As discussed herein, a “security consumer” may include any user desiringto have a security task completed by a security provider. As discussedherein, a “security task” may include any service, task, or the likewhere a security presence in desired. For example, a security consumermay desire to have a security provider for private security, travelsecurity, property security, venue security (e.g., concerts, sportingevents, church services, etc.), and/or the like.

As discussed herein, a “security provider” may include any suitableuser, agency, service provider, or the like offering security services.For example, a security provider may include an off-duty governmentemployee such as a police officer, a firefighter, or the like. As afurther example, a security provider may include a provider of healthservices, such as an emergency medical technician (EMT), paramedic,ambulance technician, or the like. As a further example, a securityprovider may include a provider of private security services, such as asecurity guard or the like.

As discussed herein, a “third party system” may include users, devices,systems, and the like configured to perform various operations for thesecurity marketplace. For example, a third party system may include apolice department, a fire station, a government authority, or the like,associated with the security provider. As a further example, a thirdparty system may include a provider of background check services, aconsumer credit reporting company, a publicly available database, and/orthe like. An exemplary provider of background check services may includeBEENVERIFIED® offered by BeenVerified, Inc., TRUTHFINDER® offered byTruthFinder, Inc., INSTANT CHECKMATE® offered by Instant Checkmate,Inc., PEOPLEFINDERS™ offered by Confi-Chek, Inc., etc. As a furtherexample, a third party system may include a payment processing system, apayment settling system, a bank, a credit union, or the like. In thatregard, the third party system may include a traditional payment networkor service that presently accommodate transactions for credit cards,debit cards, and/or other types of transaction accounts or transactioninstruments (e.g., checking accounts, savings accounts, etc.).

In a practical application, the security provider may be an off-dutypolice officer. Typically, off-duty police officers are subject tolimitations when seeking to provide off-duty security tasks (e.g., atask policy, as discussed further herein). The limitations may begoverned by the police department the police officer is employed with,and/or local, state, or Federal government policies. For example,off-duty police officers may be restricted by the amount of time theyprovide off-duty security tasks on a daily, weekly, monthly, and/oryearly basis (e.g., 20 hours a month, 10 hours a week, 4 hours a day,etc.). Typically, the task policy is enforced via self-reporting by theoff-duty police officer and/or manual tracking by a police department.As a result, completion of security tasks may be inaccurately reportedor tracked. Inaccurate reporting and/or tracking may lead to theoff-duty police officer working an unsafe number of hours off-duty,which may lead to health problems for the police officer and/or createan unsafe environment at the police department or in public. In thatregard, the practical application disclosed herein provides a solutionto a real, technical problem typically found in reporting, tracking, andenforcing task policies.

In various embodiments, the system further improves the functioning of acomputer-based system or network (e.g., security marketplace). Forexample, by automating communications between a service consumer and aservice provider, generation of service tasks, and reporting ofcompleted service tasks, as opposed to needing users to manually inputdata, communicate between parties, and self-report completed tasks,users in the system perform less computer functions and provide lessinput, which saves on data storage and memory, thus speeding processingin the computer-based system or network. Additionally, by enabling acentral repository responsible for all stages of a security task, thesecurity of the communications between the parties is improved, whichdecreases the risk of the computer-based system or network, or the dataitself, from being compromised.

In various embodiments, the system may further improve the integrity andavailability of data. As previously discussed, typically a task policyis enforced via self-reporting by the off-duty police officer and/ormanual tracking by a police department. The self-reporting may includemanually completing written forms or keeping unorganized notes. Themanual completion may be inaccurate. The manually completed written formor notes may be kept in a physical file, although may often also bediscarded on an annual basis or otherwise lost. In that respect, thesystem may improve the integrity and availability of data by maintaininga central repository of data, and by automating and maintainingreporting of completed service tasks.

In various embodiments, and with reference to FIG. 1A, a system 100 fora security marketplace is disclosed. System 100 may comprise one or moreof a security consumer device 110, a security provider device 120, athird party system 130, and/or a security marketplace 140. Securitymarketplace 140 may enable communications between security consumerdevice 110, security provider device 120, and/or third party system 130,as discussed further herein.

In various embodiments, security consumer device 110 (e.g., a consumerdevice, a security consumer device, etc.) may be configured to allow asecurity consumer to interact with security marketplace 140, initiatethe generation of one or more security tasks, and perform additionaloperations as discussed further herein. Security consumer device 110 maybe in electronic communication with security marketplace 140. In variousembodiments, security consumer device 110 may also be in electroniccommunication with security provider device 120. Security consumerdevice 110 may comprise any combination of hardware and/or softwarecomponents. For example, security consumer device 110 may comprisehardware such as a processing unit, a communications unit, a memoryunit, an input device, and/or an output device. Security consumer device110 may also comprise software configured to manage and/or interact withthe hardware components, such as, for example, an operating system, userinterfaces, software applications, and/or the like. For example,security consumer device 110 may be a computing device such as a server,a computer-based system, a portable computer-based system (e.g., alaptop, a notebook, a hand held computer, a tablet, a personal digitalassistant, etc.), a cellular phone, a smart phone (e.g., IPHONE®,BLACKBERRY®, ANDROID®, etc.), a wearable device (e.g., a smart watch,smart glasses, etc.), an internet of things (IoT) device, and/or anyother device capable of transmitting and/or receiving data over anetwork.

In various embodiments, and with reference to FIG. 2A, a securityconsumer device 110 may comprise a consumer user interface (UI) 215.Consumer UI 215 may be configured to allow security consumer device 110to interact with security marketplace 140 (with brief reference to FIG.1A). Consumer UI 215 may comprise software, a mobile application, a webinterface, or the like. Consumer UI 215 may comprise a graphical userinterface configured to allow the security consumer to input and viewdata. In various embodiments, consumer UI 215 may be hosted by securitymarketplace 140 (with brief reference to FIG. 1A) and/or via a webserver. In various embodiments, consumer UI 215 may comprise astandalone software application installed on security consumer device110.

In various embodiments, and with reference again to FIG. 1A, securityprovider device 120 (e.g., a provider device, a security providerdevice, etc.) may be configured to enable a security provider tointeract with security marketplace 140, accept and complete one or moresecurity tasks, and perform additional operations as discussed furtherherein. Security provider device 120 may be in electronic communicationwith security marketplace 140. In various embodiments, security providerdevice 120 may also be in electronic communication with securityconsumer device 110 and/or third party system 130. Security providerdevice 120 may comprise any combination of hardware and/or softwarecomponents. For example, security provider device 120 may comprisehardware such as a processing unit, a communications unit, a memoryunit, an input device, and/or an output device. Security provider device120 may also comprise software configured to manage and/or interact withthe hardware components, such as, for example, an operating system, userinterfaces, software applications, and/or the like. For example,security provider device 120 may be a computing device such as a server,a computer-based system, a portable computer-based system, a cellularphone, a smart phone, a wearable device, an internet of things (IoT)device, and/or any other device capable of transmitting and/or receivingdata over a network.

In various embodiments, a security provider device 120 may also comprise(or be in communication with) equipment or other devices carried by thesecurity provider. For example, and with reference to FIG. 1B, asecurity provider device 120 may comprise or be in communication withone or more secondary security provider devices, such as a firstsecondary security provider device 122-1 and a second secondary securityprovider device 122-2. In that respect, a security provider may have aplurality of security provider devices.

A secondary security provider device may comprise any device carried byor under control of the security provider that is in communication withsecurity provider device 120 and/or security marketplace 140. Forexample, one or more secondary security provider devices may be inelectronic communication with (the primary) security provider device120. One or more secondary security provider devices may be inelectronic communication with security marketplace 140. One or moresecondary security provider devices may be in electronic communicationwith each other.

In various embodiments, a secondary security provider device maycomprise a camera or series of cameras, such as, for example, a homesecurity system (e.g., a surveillance camera), a drone, a body-worncamera, or the like. In that regard, the secondary security providerdevice may be configured to capture images, videos, and/or audio data.The secondary security provider device may include one or more camerasand/or microphones configured to capture the images, videos, and/oraudio data. In various embodiments, a secondary security provider devicemay comprise a weapon or electronic device such as a conductedelectrical weapon (CEW).

In various embodiments, a secondary security provider device may beassignable and unique to one or more security providers. For example, asecondary security provider device may be associated with a uniqueidentifier (e.g., a unique number, alphanumeric string, MAC address,etc.). In response to a security provider being assigned or provided thesecondary security provider device, system 100 may assign and associatethe secondary security provider device with the security provider. Forexample, security marketplace 140 may associate the unique identifier ofthe secondary security provider device with a provider identifierassociated with the security provider. Security marketplace 140 maystore the association in a provider profile associated with the securityprovider, as discussed further herein.

In various embodiments, in a practical application the service providermay be an off-duty law enforcement officer. A secondary securityprovider device may comprise a body worn camera (e.g., secondarysecurity provider device 122-1, as depicted in FIG. 1B) and/or a CEW(e.g., secondary security provider device 122-2, as depicted in FIG.1B). Security provider device 120 may comprise a computer-based system,such as a smart phone. Security provider device 120 may be in electroniccommunication with one or more of secondary security provider devices122-1, 122-2. Security provider device 120 may be configured toinstruct, transmit data to, receive data from, and/or providecommunications capabilities to one or more of secondary securityprovider devices 122-1, 122-2.

For example, security provider device 120 may instruct secondarysecurity provider device 122-1 to begin recording video and/or audio, orto stop recording video and/or audio. Security provider device 120 mayreceive recorded video and/or audio data from secondary securityprovider device 122-1 and may transmit (e.g., upload, stream, etc.) therecorded video and/or audio data to security marketplace 140 (and/ordirectly to security consumer device 110).

As a further example, security provider device 120 may receive anactivation signal from secondary security provider device 122-2. In thatregard, secondary security provider device 122-2 may be configured totransmit the activation signal in response to secondary securityprovider device 122-1 being drawn from a holster, activated to deployprojectiles, and/or response to any other suitable or defined event. Inresponse to receiving the activation signal, security provider device120 may instruct secondary security provider device 122-1 to beginrecording video and/or audio data. Security provider device 120 mayreceive recorded video and/or audio data from secondary securityprovider device 122-1 and may transmit (e.g., upload, stream, etc.) therecorded video and/or audio data, and/or data regarding the activationsignal, to security marketplace 140 (and/or directly to securityconsumer device 110).

In various embodiments, and with reference to FIG. 2B, a securityprovider device 120 may comprise a provider user interface (UI) 225and/or location services 227. In various embodiments, security providerdevice 120 may further comprise a camera configured to digitally capturean image (e.g., a static image, a video, etc.) from outside securityprovider device 120, a microphone configured to capture audio fromoutside security provider device 120, and/or a speaker configured tooutput audio.

Provider UI 225 may be configured to allow security provider device 120to interact with security marketplace 140 (with brief reference to FIG.1A). Provider UI 225 may comprise software, a mobile application, a webinterface, or the like. Provider UI 225 may comprise a graphical userinterface configured to allow the security provider to input and viewdata. In various embodiments, provider UI 225 may be hosted by securitymarketplace 140 (with brief reference to FIG. 1A) and/or accessible viaa web server. In various embodiments, provider UI 225 may comprise astandalone software application (e.g., software application, mobileapplication, etc.), installed on security provider device 120.

Location services 227 may comprise software and/or hardware componentson security provider device 120. Location services 227 may be configuredto provide location details for security provider device 120. Forexample, location services 227 may comprise an onboard globalpositioning system (GPS) which provides location (e.g., coordinates) ofsecurity provider device 120. Location service 227 may also comprise acompass which provides a direction of view or movement of securityprovider device 120, and/or an accelerometer which may detect a speedand/or acceleration of movement of security provider device 120.Collectively, the information collected by location services 227 may bereferred to as “location information.” Location services 227 may alsocomprise tools, software, and the like configured to gather, associate,store, and/or transmit the location information.

In various embodiments, and with reference again to FIG. 1A, third partysystem 130 may be configured to enable a third party to interact withsecurity marketplace 110. Third party system 130 may be in electroniccommunication with security marketplace 110. Third party system 130 mayalso be in electronic communication with security provider device 120.Third party system 130 may comprise any combination of hardware and/orsoftware components. For example, third party system 130 may comprisehardware such as a processing unit, a communications unit, a memoryunit, an input device, and/or an output device. Third party system 130may also comprise software configured to manage and/or interact with thehardware components, such as, for example, an operating system, userinterfaces, software applications, databases, and/or the like. Forexample, third party system 130 may be a computing device such as aserver, a computer-based system, a portable computer-based system, acellular phone, a smart phone, a wearable device, an internet of things(IoT) device, and/or any other device capable of transmitting and/orreceiving data over a network.

In various embodiments, and with reference to FIG. 2C, a third partysystem 130 may comprise a reporting receiver system 232, a consumerverification system 234, a provider verification system 236, and/or apayment processing system 238. In various embodiments, system 100 maycomprise one or more third party systems 130 associated with each of theabove systems (e.g., separate reporting receiver system 232, consumerverification system 234, provider verification system 236, paymentprocessing system 238, etc.). In various embodiments, one or more of thethird party systems 130 may also comprise one or more of the abovesystems. For example, a third party system 130 may comprise consumerverification system 234 and provider verification system 236 (e.g., abackground check system). As a further example, a third party system 130may comprise a reporting receiver system 232 and a provider verificationsystem 236 (e.g., a police department system). Each system 232, 234,236, 238 may comprise any combination of hardware, software, and/ordatabase components described herein.

Reporting receiver system 232 may be configured to receive and/orprocess security task provider reports received from securitymarketplace 140 (with brief reference to FIG. 1A). For example,reporting receiver system 232 may be at a police department, firestation, government agency building, or the like, or accessible by thepolice department, fire station, government agency building, or thelike. Each security task provider report may be associated with asecurity provider. The security task provider report may comprise dataof security tasks completed by the security provider, such as, forexample, a task title, a task description, a task location, a task date,a task time, a total task time (e.g., weekly, monthly, etc.), etc.Reporting receiver system 232 may be configured to compare the securitytask provider report against a security task policy to determine whetherthe security provider is in violation of the security task policy (e.g.,a total task time of 20 hours in a month would violate a security taskpolicy specifying a maximum of 15 hours in a month).

Consumer verification system 234 may be configured to provideverification services for a security consumer. Consumer verificationsystem 234 may provide the verification services during a consumerregistration, and/or at any other time during the lifecycle of asecurity consumer's active registration. For example, consumerverification system 234 may be configured to verify consumer data (e.g.,name, address, telephone number, employment data, etc.). As used herein,verifying consumer data may include verifying that the consumer data iscomplete and/or accurate, and/or providing background check servicesbased on the consumer data. Consumer verification system 234 maycomprise any entity, system, service, or the like capable of verifyingthe consumer data. For example, consumer verification system 234 mayinclude a provider of background check services, a consumer reportingagency, a consumer credit reporting company, a public database, and/orthe like.

Provider verification system 236 may be configured to provideverification services for a security provider. Provider verificationsystem 236 may provide the verification services during a providerregistration, and/or at any other time during the lifecycle of asecurity provider's active registration. For example, providerverification system 236 may be configured to verify provider data, suchas provider personal data (e.g., name, address, telephone number,employment data, etc.), provider employment data (e.g., employmentstatus, government agency employed with, rank, etc.), securitycredentials (e.g., security experience, tenure, certifications, etc.),and/or the like. As used herein, verifying provider data may includeverifying that the provider data is complete and/or accurate, providingbackground check services based on the provider data, verifyingemployment data or security credentials, and/or the like. Providerverification system 236 may comprise any entity, system, service, or thelike capable of verifying the provider data. For example, providerverification system 236 may include a provider of background checkservices, a consumer reporting agency, a consumer credit reportingcompany, a public database, and/or the like. As a further example,provider verification system 236 may include a government agency (e.g.,police department, fire station, etc.) capable of verifying employmentstatus, security credentials, and/or the like.

Payment processing system 238 may be configured to receive, process, andcomplete security task payments received from security marketplace 140(with brief reference to FIG. 1A). Payment processing system 238 mayalso be configured receive consumer payment information from securitymarketplace 140 (with brief reference to FIG. 1A), validate the consumerpayment information, and return a consumer payment validationnotification, as discussed further herein. Payment processing system 238may comprise a typical payment processing system, a payment settlingsystem, a bank, or the like, as discussed further herein.

In various embodiments, and with reference again to FIG. 1A, securitymarketplace 140 may be configured to provide various securitymarketplace services, as discussed further herein. For example, securitymarketplace 140 may be configured to provide registration services forsecurity consumers and/or security providers. Security marketplace 140may be configured to receive a security task from a security consumerand enable a security provider to complete the security task. Securitymarketplace 140 may be configured to process security task paymentsreceived in response to a security provider completing a security task.Security marketplace 140 may be configured to provide security providerreporting capabilities. Security marketplace 140 may also be configuredto provide security task monitoring capabilities and technology, such asvideo streaming, location tracking, and/or the like.1

Security marketplace 140 may be in electronic communication withsecurity consumer device 110, security provider device 120, and/or thirdparty system 130. Security marketplace 140 may comprise any combinationof hardware and/or software components. For example, securitymarketplace 140 may comprise hardware such as a processing unit, acommunications unit, a memory unit, an input device, and/or an outputdevice. Security marketplace 140 may also comprise software configuredto manage and/or interact with the hardware components, such as, forexample, an operating system, user interfaces, software applications,databases, and/or the like.

In various embodiments, security marketplace 140 may comprise at leastone computing device in the form of a computer or processor, or a set ofcomputers and/or processors, although other types of computing units orsystems may be used, such as, for example, a server, a web server, apooled server, an application server, a computer-based system, and/orthe like. Security marketplace 140 may also include one or more datacenters, cloud storages, or the like, and may include software, such asapplication programming interfaces (APIs), software development kits(SDKs), web services, executables, or the like configured to performvarious operations, functions, and steps discussed herein. In variousembodiments, security marketplace 140 may be computer based, and maycomprise a processor, a tangible non-transitory computer-readablememory, and/or a network interface, along with other suitable systemsoftware and hardware components. Instructions stored on the tangiblenon-transitory memory may allow security marketplace 140 to performvarious operations, functions, and/or steps, as described herein.

Security marketplace 140 may comprise one or more hardware, software,and/or database components configured to perform various services,operations, functions, and/or steps, as described herein. For example,in accordance with various embodiments and with reference to FIG. 3, asecurity marketplace 140 may comprise one or more of a consumer database341, a provider database 342, a security task database 345, amarketplace orchestration engine 350, a verification system 360, areporting system 370, a payment system 380, and/or a marketplaceservices system 390.

Consumer database 341 may be configured to store and maintain consumerprofiles. A consumer profile may be associated with a security consumer,and may be generated during a consumer registration process. Theconsumer profile may comprise a consumer identifier generated during theconsumer registration process and configured to uniquely identify theconsumer. The consumer profile may also comprise consumer data, consumerpayment information, consumer tasks, and/or any other securityconsumer-based data. The consumer tasks may comprise a task identifierand a task status. The task identifier may be associated with a securitytask stored in security task database 345. The task status may indicatethe current status of the security task associated with the taskidentifier (e.g., active, complete, etc.). The consumer profile may alsocomprise a consumer rating, provider feedback on the consumer, and/orthe like. Consumer database 341 may store, maintain, and/or encrypt orprotect the data using any suitable technique.

Provider database 342 may be configured to store and maintain providerprofiles. A provider profile may be associated with a security provider,and may be generated during a provider registration process. Theprovider profile may comprise a provider identifier generated during theprovider registration process and configured to uniquely identify theprovider. The provider profile may also comprise provider data, aprovider task policy, provider completed tasks (e.g., a task identifier,a task time, etc.), provider completed task time, and/or any othersecurity provider-based data. The provider profile may also comprise aprovider rating, consumer feedback on the provider, and/or the like.Provider database 342 may store, maintain, and/or encrypt or protect thedata using any suitable technique.

Security task database 345 may be configured to store and maintainsecurity task data (e.g., security tasks). The security task data maycomprise a task identifier generated during creation of the securitytask. The security task data may also comprise a task status, a tasktype, a task description, a task location (e.g., venue, address, ageofence, etc.), a task requirement, a task allotted time (e.g., 2hours, 3-6 hours, etc.), a task payout (e.g., $500.00, $50.00/hour,etc.), and/or any other security task-based data. A geofence maycomprise or define a virtual perimeter associated with a real-worldgeographic area. A geofence may comprise a fixed radius around a pointlocation or may comprise a predefined set of boundaries. The taskrequirement may comprise data requested by a security consumer duringcreation of the security task, such as, for example, requested securityprovider credentials (e.g., rank, tenure, certifications, unit, etc.),travel requirements, attire requirement (e.g., in uniform, casualclothes, etc.), video streaming request, and/or the like. The task typemay be selectable from the system (e.g., via a drop-down box ofavailable task types) or may be input by a security consumer. The taskrequirement may also comprise data or instructions of services to beperformed during a security task, such as, for example, video and/oraudio streaming, location tracking, or the like. Security task database345 may store, maintain, and/or encrypt or protect the data using anysuitable technique.

Marketplace orchestration engine 350 may be configured as a centralorchestration means configured to transmit and receive data in securitymarketplace 140. For example, marketplace orchestration engine 350 maytransmit and retrieve data from consumer database 341, provider database342, and/or security task database 345. Marketplace orchestration engine350 may also instruct, transmit data to, and receive data fromverification system 360, reporting system 370, payment system 380,and/or marketplace services system 390, as discussed further herein.

Verification system 360 may be configured to provide verificationservices for consumer registrations and provider registrations. Forexample, in response to a security consumer or a security providersubmitting a marketplace registration request, verification system 360may be configured to communicate with a third party system 130 (withbrief reference to FIGS. 1 and 2C) to verify the consumer data orprovider data received from the marketplace registration request.

Reporting system 370 may be configured to provide reporting capabilitiesin security marketplace 140. For example, reporting system 370 may beconfigured to generate a security provider task report. The securityprovider task report may be generated in response to a security providercompleting a security task and/or at a defined reporting time (e.g.,daily, weekly, monthly, etc.). The security provider task report may begenerated using any suitable technique, and may be generated orconverted into in any desired format (e.g., XML file, world document,spreadsheet, email, text message, etc.). Reporting system 370 maytransmit the security provider task report to a third party system 130(with brief reference to FIGS. 1 and 2C) and/or to security providerdevice 110 (with brief reference to FIG. 1A).

Payment system 380 may be configured to process a security task payment.For example, payment system 380 may process a security task payment inresponse to a security provider completing a security task, or based ona defined payment time (e.g., payment at the end of each month). Paymentsystem 380 may be configured to communicate with a third party system130 (with brief reference to FIGS. 1 and 2C) to complete the processingof the payment.

Marketplace services system 390 may be configured to provide variousservices available through security marketplace 140. For example,marketplace services system 390 may be configured to provide videostreaming services from a security provider device (e.g., an onboardcamera, body camera, etc.) to a security consumer device. Marketplaceservices system 390 may provide the streaming services using anysuitable protocol (e.g., Real-Time Messaging Protocol (RTMP), HTTP-basedprotocols, etc.), and including any compression or streaming techniques.Marketplace services system 390 may provide the streaming services inreal-time or near real-time. As a further example, marketplace servicessystem 390 may provide location services such as real-time tracking, GPStracking, or the like. As a further example, marketplace services system390 may provide services for the security provider device, such as, forexample, activation of a CEW, or the like. As a further example,marketplace services system 390 may provide travel services for securitytasks requiring travel (e.g., car, air, hotel, etc.). Marketplaceservices system 390 may communicate with, or redirect to, a third-partytravel service (e.g., EXPEDIA®, TRAVELOCITY®, a public air travelbooking platform, a private air travel booking platform, a hotel bookingplatform, etc.).

Referring now to FIGS. 4-9B the process flows depicted are merelyembodiments and are not intended to limit the scope of the disclosure.For example, the steps recited in any of the method or processdescriptions may be executed in any order and are not limited to theorder presented. It will be appreciated that the following descriptionmakes appropriate references not only to the steps depicted in FIGS.4-9B, but also to the various system components as described above withreference to FIGS. 1A-3.

In various embodiments, and with specific reference to FIG. 4, a method400 for registering a security consumer for a security marketplace isdisclosed. The system may receive a consumer marketplace registrationrequest (step 402). For example, a security consumer may interact withsecurity consumer device 110 to transmit a consumer marketplaceregistration request to security marketplace 140 (e.g., via marketplaceorchestration engine 350). The consumer marketplace registration requestmay comprise consumer data and/or consumer payment information. Theconsumer data may comprise data associated with the security consumer,such as, for example, name, company, title, company address, homeaddress, contact phone number, etc. The consumer payment information maycomprise data indicating a payment account that the security consumerdesires to use to pay for security tasks, such as a checking account, asavings account, a credit card number, etc. The consumer paymentinformation may comprise an account number, a routing number, a creditcard number, an expiration date, and/or any other payment information.The consumer marketplace registration request may also comprise ausername, a password, a biometric input, or the like.

The system may verify consumer data (step 404) from the consumermarketplace registration request. For example, security marketplace 140(via marketplace orchestration engine 350 and/or verification system360) may transmit the consumer data to a third party system 130. Thirdparty system 130 may verify the consumer data using any suitabletechnique. In response, third party system 130 may transmit to securitymarketplace 140 a consumer verification notification. The consumerverification notification may comprise data indicating that theverification process passed or failed, or may provide a risk score orsimilar notifier of consumer worthiness.

The system may validate payment information (step 406) from the consumermarketplace registration request. For example, security marketplace 140(via marketplace orchestration engine 350 and/or verification system 360or payment system 380) may transmit the payment information to a thirdparty system 130. Third party system 130 may validate the paymentinformation using any suitable technique. In response, third partysystem 130 may transmit to security marketplace 140 a consumer paymentvalidation notification. The consumer payment validation notificationmay comprise data indicating that the validation process passed orfailed. In response to the payment information failing validation,security marketplace 140 may prompt security consumer device 110 toreenter payment information or to select another form of payment.

In response to verifying the consumer data and/or validating the paymentinformation, the system may update the consumer database (step 408) tocomplete the consumer marketplace registration request. For example,security marketplace 140 (via marketplace orchestration engine 350) maygenerate a consumer profile. The consumer profile may comprise aconsumer identifier configured to uniquely identify the securityconsumer. The consumer profile may comprise the consumer data (or aportion of the consumer data) and the payment information. Securitymarketplace 140 (via marketplace orchestration engine 350) may store theconsumer profile in consumer database 341. In response to updating theconsumer database, the system may return to the security consumer aregistration success notification.

In various embodiments, and with specific reference to FIG. 5, a method500 for registering a security provider for a security marketplace isdisclosed. The system may receive a provider marketplace registrationrequest (step 502). For example, a security provider may interact withsecurity provider device 120 to transmit a provider marketplaceregistration request to security marketplace 140 (e.g., via marketplaceorchestration engine 350). The provider marketplace registration requestmay comprise provider data. Provider data may comprise provider personaldata (e.g., name, address, telephone number, employment data, etc.),provider employment data (e.g., employment status, government agencyemployed with, rank, etc.), security credentials (e.g., securityexperience, tenure, certifications, etc.), and/or the like. The providermarketplace registration request may also comprise a provider paymentaccount. The provider payment account may comprise data associated withthe bank account (e.g., checking account, savings account, etc.) thatthe provider desires security task payments to be transmitted to. Theprovider marketplace registration request may also comprise a username,a password, a biometric input, or the like. The provider marketplaceregistration request may also comprise data regarding secondary securityprovider devices used by or associated with the security provider, suchas a device type (e.g., body worn camera, CEW, surveillance camera,etc.), a device identifier (e.g., unique identifier associated with thesecondary security provider device), and/or the like.

The system may verify provider data (step 504) from the providermarketplace registration request. For example, security marketplace 140(via marketplace orchestration engine 350 and/or verification system360) may transmit the provider data to (one or more) third party system130. Third party system 130 may verify the provider data using anysuitable technique. In response, third party system 130 may transmit tosecurity marketplace 140 a provider verification notification. Theprovider verification notification may comprise data indicating that theverification process passed or failed. In response to the providerverification failing, the provider verification notification may alsocomprise data indicating the provider data that was unable to beverified, or that failed the verification process. In variousembodiments, the system may also validate the provider payment account.The system may validate the provider payment account using a similarprocess to that described in step 406 of FIG. 4.

The system may retrieve a provider task policy (step 506). The providertask policy may be provided with the provider marketplace registrationrequest. Security marketplace 130 (via marketplace orchestration engine350) may also communicate with a third party system 130 (e.g., a policedepartment, government authority, etc.) to retrieve the task policy.

In response to verifying the provider data and/or retrieving the taskpolicy, the system may update the provider database (step 508) tocomplete the provider marketplace registration request. For example,security marketplace 140 (via marketplace orchestration engine 350) maygenerate a provider profile. The provider profile may comprise aprovider identifier configured to uniquely identify the securityprovider. The provider profile may comprise the provider data (or aportion of the provider data), the provider payment account, and/or thetask policy. Security marketplace 140 (via marketplace orchestrationengine 350) may store the provider profile in provider database 342. Inresponse to updating the provider database, the system may return to thesecurity provider a registration success notification.

In various embodiments, and with specific reference to FIG. 6, a method600 for generating a security task is disclosed. The system may receivea security task request (step 602). For example, security marketplace140 (via marketplace orchestration engine 350) may receive the securitytask request from security consumer device 110. The security taskrequest may comprise a task type (e.g., venue security, travel security,personal security, etc.), a task description, a task location (e.g.,venue, address, a geofence, etc.), a task requirement, a task allottedtime (e.g., 2 hours, 3-6 hours, etc.), a task payout (e.g., $500.00,$50.00/hour, etc.), and/or any other security task-based data. The taskrequirement may comprise requirements input by the security consumer,such as, for example, requested security provider credentials, travelrequirements, attire requirements, video streaming request (e.g.,request to provide video data), audio streaming request (e.g., requestto provide audio data), location tracking, and/or the like. The taskpayout may be input by the security consumer. In various embodiments,the task payout may be selectable based on task type or taskrequirements (e.g., payout tiers based on the task types and/or taskrequirements).

In response to receiving the security task request, the system mayvalidate the security task request (step 604). Security marketplace 140(via marketplace orchestration engine 350) may be configured to validatethe security task request. For example, security marketplace 140 maycommunicate with consumer database 341 to verify that the securityconsumer transmitting the request comprises a consumer profile and/or isin good standing. Security marketplace 140 may also validate thesecurity task request by verifying that the security task requestcomprises all required inputs.

The system may generate a security task based on the security taskrequest (step 606). Security marketplace 140 (via marketplaceorchestration engine 350) may be configured to generate the securitytask based on the security task request. Security marketplace 140 maygenerate and assign a task identifier to uniquely identify the securitytask. The security task may comprise the consumer identifier associatedwith the security consumer transmitting the request. The security taskmay comprise the task status, the task type, the task description, thetask location, the task requirement, the task allotted time, and/or anyother security task-based data from the security task request.

The system may store the security task in the security task database(step 608). Security marketplace 140 (via marketplace orchestrationengine 350) may be configured to store the security task in securitytask database 345.

In various embodiments, and with specific reference to FIG. 7, a method700 for completing a security task is disclosed. The system may transmita security task alert (step 702). The system may transmit the securitytask alert in response to the security task being generated and/orstored. The system may transmit the security task alert based on apredefined alert time (e.g., once an hour, once a day, etc.). The systemmay transmit the security task alert to a security provider. Forexample, the system may directly transmit the security task alert to asecurity provider via email, text message, or the like. The system mayalso transmit the security task alert by providing the security taskalert on a task board or similar web-based or mobile app-based portalconfigured to provide information on one or more security task alerts tosecurity providers.

The security task alert may also be transmitted to one or securityproviders based on a match between a provider profile and the securitytask. The system may transmit the security task alert to a third partysystem (e.g., police department, government authority, etc.) having asecurity provider registered with the system. In that regard, the thirdparty system may control who the security task is assigned to (e.g.,based on tenure, randomized, fixed rotation, by unit, etc.). Securitymarketplace 140 (via marketplace orchestration engine 350) may beconfigured to generate and transmit the security task alert. Forexample, the security task alert may be transmitted to security providerdevice 120. The security task alert may comprise data indicating asecurity task is available. The security task alert may also comprisedata associated with the security task, such as, for example, the taskidentifier, the task type, the task description, or the like.

The system may receive a security task acceptance (step 704). Securitymarketplace 140 (via marketplace orchestration engine 350) may beconfigured to receive the security task acceptance from a securityprovider device 120. For example, a security provider may interact withsecurity provider device 120 to accept a security task in response toreceiving the security task alert. The security provider, via securityprovider device 120, may also browse security marketplace 140 (viamarketplace orchestration engine 350 and security task database 345) toview available security tasks. The security task acceptance may comprisethe task identifier and the provider identifier of the security provideraccepting the security task.

The system may validate the security task acceptance (step 706).Security marketplace 140 (via marketplace orchestration engine 350) maybe configured to validate the security task acceptance. For example,security marketplace 140 may validate the security task acceptance basedon comparison of the provider profile and task policy. Securitymarketplace 140 (via marketplace orchestration engine 350 and providerdatabase 342) may retrieve the provider profile (based on provideridentifier). Security marketplace 140 may compare the provider completedtask time (e.g., the total time spent completing security tasks) to thetask policy to determine whether the security provider may complete thesecurity task without violating the task policy. Validation may alsoinclude transmitting the security task acceptance to the securityconsumer (based on consumer identifier), and requiring affirmation fromthe security consumer. In that regard, the security consumer may decideto deny the security task acceptance, and reopen the security task to adifferent security provider. In response to the security consumerreceiving a plurality of security task acceptances, the securityconsumer may select one (or more) of the security task acceptances toproceed with.

In response to validating the security task acceptance, the system maytransmit a security task acceptance notification (step 708). The systemmay transmit the security task acceptance notification to the securityconsumer and the security provider. For example, security marketplace140 (via marketplace orchestration engine 350) may be configured totransmit the security task acceptance notification to security consumerdevice 110 and security provider device 120 (and/or third party 130associated with the security provider). The security task acceptancenotification may comprise consumer data and provider data to enablecommunication between the parties. Security marketplace 140 (viamarketplace orchestration engine 350) may update the security task insecurity task database 345 as assigned to the security provider.Security marketplace 140 (via marketplace orchestration engine 350) mayalso update consumer database 341 and/or provider database 342 toreflect the assignment.

During completion of the security task, or before completion of thesecurity task, security marketplace 140 (via marketplace services system390) may be configured to provide marketplaces services based on therequirements of the security task. For example, in response to thesecurity task requiring video streaming capabilities, securitymarketplace 140 (via marketplace services system 390) may provide videostreaming services to enable video to be streamed from security providerdevice 120 to security consumer device 110. As a further example, inresponse to the security task requiring travel, security marketplace 140(via marketplace services system 390) may provide travel services to thesecurity consumer and/or security provider to book the travel.

For example, and in accordance with various embodiments, a marketplaceservice may comprise a video and/or audio request, a location trackingrequest, and/or the like. The marketplace service may be provided basedon task requirements, as discussed further herein. For example, inresponse to a task requirement comprising a video streaming request,security marketplace 140 may be configured to provide video servicesduring completion of the security task. Security marketplace 140 may beconfigured to provide the marketplace service using any suitable processor technique.

For example, in accordance with various embodiments and with referenceto FIG. 9A, a method 900 for a consumer activation of a securityprovider device is disclosed. The system may receive a service accessrequest (step 902). Security marketplace 140 may be configured toreceive the service access request. The service access request may betransmitted to the system by a security consumer device (e.g., securityconsumer device 110). The service access request may comprise dataindicating a marketplace service that a security consumer desires toconsume, activate, and/or receive (e.g., via security consumer device110). For example, the service access request may comprise the taskidentifier and a marketplace service selection, such as a video request,an audio request, a location tracking request, and/or the like.

The system may determine a service availability (step 904). Securitymarketplace 140 may be configured to determine the service availability.The system may determine the service availability using any suitabletechnique. For example, the system may determine whether the service isavailable (step 906-1) or not available (step 906-2). Determiningwhether the service is available or not available may includedetermining whether a security provider device is already providing theservice to security marketplace 140 (e.g., security provider device 120is already transmitting or otherwise providing video, audio, locationinformation, or the like to security marketplace 140).

In response to the system determining that the service is not available(step 906-2), the system may transmit a service request (step 908).Security marketplace 140 may be configured to transmit the servicerequest to a security provider device (e.g., a security provider device120). The service request may comprise data or instructions to thesecurity provider device to provide the marketplace service selection.For example, in response to the marketplace service selection comprisinga video service, the service request may comprise instructions to thesecurity provider device to begin recording video and transmit the videoto the system (e.g., security marketplace 140 and/or directly tosecurity consumer device 110).

In response to receiving the service request, the security providerdevice may activate a corresponding service. For example, the securityprovider device may begin recording audio and/or video, providinglocation information, or the like. In various embodiments, the securityprovider device may also prompt a security provider to confirm or acceptactivation of the service, prior to activating the service. In responseto beginning recording audio and/or video, providing locationinformation, or the like, the security provider device may transmit aservice activation notification to the system.

In various embodiments, in response to the security provider alsoincluding a secondary security provider device (e.g., secondary securityprovider device 122-1), the security provider device may instruct thesecondary security provider device to begin recording audio and/orvideo, providing location information, or the like. In response toreceiving the instruction, the secondary security provider device maybegin recording audio and/or video, providing location information, orthe like. The secondary security provider device may transmit a serviceactivation notification to the system (e.g., directly or via thesecurity provider device).

The system may receive a service activation notification (step 910).Security marketplace 140 and/or security consumer device 110 may receivethe service activation notification. The service activation notificationmay comprise data indicating that the service is being provided. Theservice activation notification may also comprise data or metadataassociated with the service activation, such as, for example, a date andtime of activation, a location information associated with theactivation, a unique identifier associated with the security providerdevice providing the service, and/or the like.

The system may provide the service (step 912). The system may providethe service in response to determining that the system is available(step 906-1) or in response to receiving the service activation (step910) from the security provider device. For example, a security providerdevice (or a secondary provider device) may provide the service directlyto the security consumer device. As a further example, the securityprovider device (or the secondary provider device) may provide theservice to the security marketplace. The security marketplace mayprovide the service directly to the security consumer device. Thesecurity marketplace may also store data (e.g., service data) regardingthe service (e.g., audio file, video file, location information file,etc.). The security marketplace may associate the service data with thesecurity task, the service activation notification, and/or any otherdata received or ingested by the security marketplace. In variousembodiments, providing the service may comprise a tangible outcomecaused by the service access request (e.g., activation of a microphoneor camera, activation of a GPS or similar location device, etc.).

As a further example, in accordance with various embodiments and withreference to FIG. 9B, a method 921 for a task activation of a securityprovider device is disclosed. The system may transmit a task requirement(step 922). For example, the task requirement may be transmittedtogether with transmitting a security task alert (e.g., step 702, withbrief reference to FIG. 7), and/or separately or combined with any otherprocess or step. Security marketplace 140 may be configured to transmitthe task requirement to security provider device 120.

A security provider device (e.g., security provider device 120) mayreceive the task requirement (step 924-1). The task requirement (e.g.,service task requirement) may comprise data and/or instructions thatcause the security provider device to perform operations based on thedetection of a task activity. For example, the task requirement maycomprise data/or instructions that cause the security provider device to(directly or indirectly) provide a service (e.g., audio, video, locationinformation, etc.) in response to detecting that the security providerdevice is within a geofence location, the security provider device has adevice time and/or date matching a security task time and/or date, a CEWin electronic communication with the security provider device hasactivation, and/or any other type of detection (e.g., activation of asurveillance alarm, occurrence of an event, increase in heart rate ofthe security provider, etc.). Providing the service may comprise atangible outcome caused by the detection (e.g., activation of amicrophone or camera, activation of a GPS or similar location device,etc.).

The security provider device may detect a task activity (step 926-1).For example, detecting the task activity may include detecting ageofence (step 928-1A), a time (step 928-1B), a CEW activation (step928-1C), and/or an other detection (step 928-1D). The security providerdevice may be configured to detect the task activity using any suitablemethod. The security provider device may also be configured to detect aplurality of task activities. For example, detecting a geofence (step928-1A) may include comparing location information of the securityprovider device against the geofence data to determine whether thesecurity provider device is within the geofence. Detecting a time (step928-1B) may include comparing a local time and/or date provided by thesecurity provider device against the time data to determine whether thetime and/or date of the security provider device is equal to or greaterthan the time data. Detecting a CEW activation (step 928-1C) may includethe security provider device receiving an activation signal that the CEWwas activated, withdrawn from its holster, or the like. The securityprovider device may detect an other detection (step 928-1D) using anysimilarly suitable process.

In various embodiments, in response to detecting the task activity, thesecurity provider device may activate a corresponding service providedby the security provider device. For example, the security providerdevice may begin recording audio and/or video, providing locationinformation, or the like. In various embodiments, the security providerdevice may also prompt a security provider to confirm or acceptactivation of the service, prior to activating the service. In responseto beginning recording audio and/or video, providing locationinformation, or the like, the security provider device may transmit aservice activation notification to the system.

In various embodiments, in response to detecting the task activity thesecurity provider device may activate a secondary security providerdevice (e.g., secondary security provider device 122-1) (step 930-1).The security provider device may be in electronic communication with thesecondary security provider device. The security provider device mayactivate the secondary security provider device using any suitablemethod or process. For example, the security provider device maytransmit an activation instruction to the secondary security providerdevice. The activation instruction may comprise instructions to activatea service. In response to receiving the activation instruction, thesecondary security provider device may activate the correspondingservice. For example, in response to receiving the activationinstruction, the secondary security provider device may begin recordingaudio and/or video, providing location information, or the like. Thesecondary security provider device may transmit a service activationnotification to the system (e.g., directly or via the security providerdevice).

The security provider device may transmit the service activationnotification (step 932-1), as previously discussed.

The system may receive a service activation notification (step 934).Security marketplace 140 and/or security consumer device 110 may receivethe service activation notification. The service activation notificationmay comprise data indicating that the service is being provided. Theservice activation notification may also comprise data or metadataassociated with the service activation, such as, for example, a date andtime of activation, a location information associated with theactivation, a unique identifier associated with the security providerdevice providing the service, an event causing the activation (e.g.,geofence, date time, CEW activation, etc.), and/or the like.

The system may provide the service (step 936). The system may providethe service in response to activating the security provider device,activating the secondary security provider device, and/or in response toreceiving the service activation (step 934). For example, a securityprovider device (or a secondary provider device) may provide the servicedirectly to the security consumer device. As a further example, thesecurity provider device (or the secondary provider device) may providethe service to the security marketplace. The security marketplace mayprovide the service directly to the security consumer device. Thesecurity marketplace may also store data (e.g., service data) regardingthe service (e.g., audio file, video file, location information file,etc.). The security marketplace may associate the service data with thesecurity task, the service activation notification, and/or any otherdata received or ingested by the security marketplace. In variousembodiments, providing the service may comprise a tangible outcomecaused by the service access request (e.g., activation of a microphoneor camera, activation of a GPS or similar location device, etc.).

With reference again to FIG. 7, the system may receive a security taskcompletion notification (step 710) in response to the security taskbeing completed. For example, security marketplace 140 (via marketplaceorchestration system 350) may receive the security task completionnotification from security consumer device 110 and/or security providerdevice 120. The security task completion notification may comprise thetask identifier, data indicating the security task was completed, aconsumer feedback about the security provider (e.g., provider rating,remarks, etc.), a provider feedback about the security consumer (e.g.,consumer rating, remarks, etc.). Security marketplace 140 (viamarketplace orchestration system 350) may update the consumer profile inconsumer database 341 to reflect the provider feedback. Securitymarketplace 140 (via marketplace orchestration system 350) may updatethe provider profile in provider database 342 to reflect the providerfeedback.

In response to receiving the security task completion notification, thesystem may authorize a security task payment (step 712). The securitytask payment may be based on the task payout specified in the securitytask. Security marketplace 140 (via marketplace orchestration system 350and payment system 380) may be configured to authorize the security taskpayment. For example, security marketplace 140 may retrieve the consumerpayment information and the provider payment account (e.g., via consumerdatabase 341 and/or provider database 342). Security marketplace 140 maycommunicate with one or more third party systems 130 to authorize andinitiate payment from the consumer account to the provider account.Third party system 130 may complete the payment using any suitabletechnique and return a payment notification in response to completingthe payment.

The system may update the security task database (step 714). Securitymarketplace 140 (via marketplace orchestration system 350) may updatethe consumer profile in consumer database 341 to reflect the providerfeedback, the security task completion, and the payout authorized.Security marketplace 140 (via marketplace orchestration system 350) mayupdate the provider profile in provider database 342 to reflect theprovider feedback, the security task completion, and the paymentauthorized. Security marketplace 140 (via marketplace orchestrationsystem 350) may update security task database 345 to mark the securitytask as completed.

In various embodiments, and with specific reference to FIG. 8, a method800 for generating a security provider task report is disclosed. Thesystem may retrieve a provider profile (step 802) based on the securitytask completion notification. For example, security marketplace 140 (viamarketplace orchestration system 350) may retrieve the provider profilefrom provider database 342 based on the provider identifier.

The system may update a provider completed task time (step 804) from theprovider profile. Security marketplace 140 (via marketplaceorchestration system 350) may update the provider completed task time inthe provider profile. The provider completed task time may be based onthe task time from the security task. The provider completed task timemay be updated to reflect the number of hours the security provider hasspent completing security tasks, post-security task completionnotification.

The system may generate a security provider task report (step 806). Thesecurity provider task report may comprise provider data indicating theidentity of the security provider and the provider completed task time.Security marketplace 140 (via marketplace orchestration system 350and/or reporting system 370) may be configured to generate the securityprovider task report.

In response to generating the security provider task report, the systemmay transmit the security provider task report (step 808). Securitymarketplace 140 (via marketplace orchestration system 350 and/orreporting system 370) may be configured to transmit the securityprovider task report. The security provider task report may betransmitted to security provider device 120. The security provider taskreport may be transmitted to a third party system 130 associated withthe security provider (e.g., police department, government authority,etc.).

In various embodiments, and with reference to FIG. 10, an exemplarycomputer-based system 1001 is disclosed. Computer-based system 1001 maybe appropriate for use in accordance with embodiments of the presentdisclosure. The accompanying description of computer-based system 1001may be applicable to servers, personal computers, mobile phones, smartphones, tablet computers, embedded computing devices, and othercurrently available or yet-to-be-developed devices that may be used inaccordance with embodiments of the present disclosure.

Computer-based system 1001 may include a processor 1002 and a systemmemory 1004 connected by a communication bus 1006. Depending on theexact configuration and type of computer-based system, system memory1004 may be volatile or nonvolatile memory, such as read only memory(“ROM”), random access memory (“RAM”), EEPROM, flash memory, or othermemory technology. Those of ordinary skill in the art and others willrecognize that system memory 1004 typically stores data and/or programmodules that are immediately accessible to and/or currently beingoperated on by processor 1002. In this regard, processor 1002 may serveas a computational center of computer-based system 1001 by supportingthe execution of instructions. Processor 1002 may comprise one or moreprocessing units, as discussed further herein. System memory 1004 maycomprise one or more memory units, as discussed further herein.

Computer-based system 1001 may include a network interface 1010comprising one or more components for communicating with other devicesand systems over a network. Embodiments of the present disclosure mayaccess basic services that utilize network interface 1010 to performcommunications using common network protocols. Network interface 1010may comprise a communications unit, as discussed further herein.

Computer-based system 1001 may also include a storage medium 1008.However, services may be accessed using a computer-based system thatdoes not include means for persisting data to a local storage medium.Therefore, storage medium 1008 depicted in FIG. 10 is optional. Storagemedium 1008 may be volatile or nonvolatile, removable or nonremovable,implemented using any technology capable of storing information such as,but not limited to, a hard drive, solid state drive, CD-ROM, DVD,BLU-RAY®, or other disk storage, magnetic tape, magnetic disk storage,and/or the like. Storage medium 1008 may include one or more memoryunits, as discussed further herein.

As used herein, the term “computer-readable medium” includes volatileand nonvolatile and removable and nonremovable media implemented in anymethod or technology capable of storing information, such ascomputer-readable instructions, data structures, program modules, orother data. In this regard, system memory 1004 and storage medium 1008depicted in FIG. 10 are examples of computer-readable media.

For ease of illustration and because it is not important for anunderstanding of the claimed subject matter, FIG. 10 does not show someof the typical components of many computer-based systems. In thisregard, computer-based system 1001 may include input devices, such as akeyboard, keypad, mouse, trackball, microphone, video camera, touchpad,touchscreen, electronic pen, stylus, and/or any other input devicedescribed herein. Such input devices may be coupled to computer-basedsystem 1001 by wired or wireless connections including RF, infrared,serial, parallel, BLUETOOTH®, USB, or other suitable connectionprotocols using wireless or physical connections.

In any of the described examples, data can be captured by input devicesand transmitted or stored for future processing. The processing mayinclude encoding data streams, which can be subsequently decoded forpresentation by output devices. Media data can be captured by multimediainput devices and stored by saving media data streams as files on acomputer-readable storage medium (e.g., in memory or persistent storageon a client device, server, administrator device, or some other device).Input devices can be separate from and communicatively coupled tocomputer-based system 1001 (e.g., a client device), or can be integralcomponents of computer-based system 1001. In some embodiments, multipleinput devices may be combined into a single, multifunction input device(e.g., a video camera with an integrated microphone).

Computer-based system 1001 may also include output devices such as adisplay, speakers, printer, and/or any other output device describedherein. The output devices may include video output devices such as adisplay or touchscreen. The output devices also may include audio outputdevices such as external speakers or earphones. The output devices canbe separate from and communicatively coupled to computer-based system1001, or can be integral components of computer-based system 1001. Inputfunctionality and output functionality may be integrated into the sameinput/output device (e.g., a touchscreen). Any suitable input device,output device, or combined input/output device either currently known ordeveloped in the future may be used with described systems.

In various embodiments, a “processing unit” as described herein maycomprising any suitable hardware and/or software-based processingcomponent. For example, a processing unit may comprise one or more of aprocessing circuit, a processor, an application specific integratedcircuit (ASIC), a controller, a microcontroller, a microprocessor, aprogrammable logic device, logic circuitry, and/or the like.

In various embodiments, a “communications unit” as described herein maycomprise any suitable hardware and/or software components capable ofenabling the transmission and/or reception of data. A communicationsunit may enable electronic communications between devices and systems. Acommunications unit may enable communications over a network. Examplesof a communications unit may include a modem, a network interface (suchas an Ethernet card), a communications port, etc. Data may betransferred via a communications unit in the form of signals which maybe electronic, electromagnetic, optical, or other signals capable ofbeing transmitted or received by a communications unit. A communicationsunit may be configured to communicate via any wired or wireless protocolsuch as a CAN bus protocol, an Ethernet physical layer protocol (e.g.,those using 10BASE-T, 100BASE-T, 1000BASE-T, etc.), an IEEE 1394interface (e.g., FireWire), Integrated Services for Digital Network(ISDN), a digital subscriber line (DSL), an 802.11a/b/g/n/ac signal(e.g., Wi-Fi), a wireless communications protocol using short wavelengthUHF radio waves and defined at least in part by IEEE 802.15.1 (e.g., theBLUETOOTH® protocol maintained by Bluetooth Special Interest Group), awireless communications protocol defined at least in part by IEEE802.15.4 (e.g., the ZigBee® protocol maintained by the ZigBee alliance),a cellular protocol, an infrared protocol, an optical protocol, or anyother protocol capable of transmitting information via a wired orwireless connection.

One or more of the system components may be in electronic communicationvia a network. As used herein, the term “network” may further includeany cloud, cloud computing system, or electronic communications systemor method that incorporates hardware and/or software components.Communication amongst the devices and systems over a network may beaccomplished through any suitable communication channel, such as, forexample, a telephone network, an extranet, an intranet, the internet, awireless communication, local area network (LAN), wide area network(WAN), virtual private network (VPN), and/or the like.

Electronic communications between the systems and devices may beunsecure. A network may be unsecure. Electronic communications disclosedherein may utilize data encryption. Encryption may be performed by wayof any of the techniques now available in the art or which may becomeavailable—e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PM,GPG (GnuPG), HPE Format-Preserving Encryption (FPE), Voltage, TripleDES, Blowfish, AES, MD5, HMAC, IDEA, RC6, and symmetric and asymmetriccryptosystems. Network communications may also incorporate SHA seriescryptographic methods, elliptic-curve cryptography (e.g., ECC, ECDH,ECDSA, etc.), and/or other post-quantum cryptography algorithms underdevelopment.

For the sake of brevity, conventional data networking, applicationdevelopment, and other functional aspects of system may not be describedin detail herein. Furthermore, the connecting lines shown in the variousfigures contained herein are intended to represent exemplary functionalrelationships and/or electronic communications between the variouselements. It should be noted that many alternative or additionalfunctional relationships or electronic communications may be present ina practical system.

In various embodiments, a “memory unit” as discussed herein may compriseany hardware, software, and/or database component capable of storing andmaintaining data. For example, a memory unit may comprise a database,data structure, memory component, or the like. A memory unit maycomprise any suitable non-transitory memory known in the art, such as,an internal memory (e.g., random access memory (RAM), read-only memory(ROM), solid state drive (SSD), etc.), removable memory (e.g., an SDcard, an xD card, a CompactFlash card, etc.), or the like.

The term “non-transitory” is to be understood to remove only propagatingtransitory signals per se from the claim scope and does not relinquishrights to all standard computer-readable media that are not onlypropagating transitory signals per se. Stated another way, the meaningof the term “non-transitory computer-readable medium” and“non-transitory computer-readable storage medium” should be construed toexclude only those types of transitory computer-readable media whichwere found in In re Nuijten to fall outside the scope of patentablesubject matter under 35 U.S.C. § 101.

Any database discussed herein may include relational, hierarchical,graphical, distributed ledger, blockchain, object-oriented structure,and/or any other database configurations. Any database may also includea flat file structure wherein data may be stored in a single file in theform of rows and columns, with no structure for indexing and nostructural relationships between records. For example, a flat filestructure may include a delimited text file, a CSV (comma-separatedvalues) file, and/or any other suitable flat file structure. Moreover, adatabase may be organized in any suitable manner, for example, as datatables or lookup tables. Each record stored in a database may be asingle file, a series of files, a linked series of data fields, and/orany other data structure or schema.

In various embodiments, an “input device” as discussed herein maycomprise hardware and/or software used to provide data, inputs, controlsignals, and the like to a computer-based system, software application,etc. For example, an input device may include a pointing device (e.g.,mouse, joystick, pointer, etc.), a keyboard (e.g., virtual or physical),a touchpad or touchscreen interface, a video input device (e.g., camera,scanner, multi-camera system, etc.), a virtual reality system, an audioinput device (e.g., microphone, digital musical instrument, etc.), abiometric input device (e.g., fingerprint scanner, iris scanner, etc.),a composite device (e.g., a device having a plurality of different formsof input), and/or any other input device.

In various embodiments, an “output device” as discussed herein maycomprise hardware and/or software configured to convert information intoa human-accessible form, for display, projection, or physicalreproduction. For example, an output device may include a display device(e.g., monitor, monochrome display, colored display, CRT, LCD, LED,projector, video card, etc.), an audio output device (e.g., speaker,headphones, sound card, etc.), a location services system (e.g., globalpositioning system (GPS), etc.), a printer (e.g., dot matrix printer,inkjet printer, laser printer, 3D printer, wide-format printer, etc.), abraille reader, a composite device (e.g., a device having a plurality ofdifferent forms of output), and/or any other output device.

Any database, system, device, server, or other components of the systemdescribed herein may consist of any combination thereof at a singlelocation or at multiple locations. For example, any database describedherein may comprise a single database or a plurality of databases(virtual partitions or physically distinct). Each database or system mayinclude any of various suitable security features, such as firewalls,access codes, encryption, decryption, compression, decompression, and/orthe like.

In various embodiments, “satisfy,” “meet,” “match,” “associated with,”or similar phrases used herein may include an identical match, a partialmatch, meeting certain criteria, matching a subset of data, acorrelation, satisfying certain criteria, a correspondence, anassociation, an algorithmic relationship, and/or the like. Similarly, asused herein, “authenticate,” “verify,” “validate,” or similar terms mayinclude an exact authentication, verification, or validation; a partialauthentication, verification, or validation; authenticating, verifying,or validating a subset of data; satisfying certain criteria; anassociation; an algorithmic relationship; and/or the like.

Benefits, other advantages, and solutions to problems have beendescribed herein with regard to specific embodiments. Furthermore, theconnecting lines shown in the various figures contained herein areintended to represent exemplary functional relationships and/or physicalcouplings between the various elements. It should be noted that manyalternative or additional functional relationships or physicalconnections may be present in a practical system. However, the benefits,advantages, solutions to problems, and any elements that may cause anybenefit, advantage, or solution to occur or become more pronounced arenot to be construed as critical, required, or essential features orelements of the disclosures. The scope of the disclosure is accordinglyto be limited by nothing other than the appended claims and their legalequivalents, in which reference to an element in the singular is notintended to mean “one and only one” unless explicitly so stated, butrather “one or more.” Moreover, where a phrase similar to “at least oneof A, B, or C” is used in the claims, it is intended that the phrase beinterpreted to mean that A alone may be present in an embodiment, Balone may be present in an embodiment, C alone may be present in anembodiment, or that any combination of the elements A, B and C may bepresent in a single embodiment; for example, A and B, A and C, B and C,or A and B and C.

Systems, methods and apparatus are provided herein. In the detaileddescription herein, references to “various embodiments,” “oneembodiment,” “an embodiment,” “an example embodiment,” etc., indicatethat the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to affect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described. After reading the description, itwill be apparent to one skilled in the relevant art(s) how to implementthe disclosure in alternative embodiments. Furthermore, no element,component, or method step in the present disclosure is intended to bededicated to the public regardless of whether the element, component, ormethod step is explicitly recited in the claims. No claim element isintended to invoke 35 U.S.C. 112(f) unless the element is expresslyrecited using the phrase “means for.” As used herein, the terms“comprises,” “comprising,” or any other variation thereof, are intendedto cover a non-exclusive inclusion, such that a process, method,article, or apparatus that comprises a list of elements does not includeonly those elements but may include other elements not expressly listedor inherent to such process, method, article, or apparatus.

What is claimed is:
 1. A method, comprising: receiving, by at least oneprocessor of a computer-based system in electronic communication with asecurity provider device, a security task acceptance associated with asecurity task; validating, by the least one processor of thecomputer-based system, the security task acceptance; and transmitting,by the least one processor of the computer-based system, a security taskacceptance notification to a security consumer device in response tovalidating the security task acceptance.
 2. The method of claim 1,wherein the security task acceptance includes a task identifier and aprovider identifier of a security provider accepting the security task.3. The method of claim 1, wherein validating the security taskacceptance includes comparing, by the least one processor of thecomputer-based system, a provider profile associated with the securitytask acceptance and a task policy.
 4. The method of claim 1, furthercomprising transmitting, by the least one processor of thecomputer-based system, a security task alert.
 5. The method of claim 1,further comprising: receiving, by the least one processor of thecomputer-based system, a security task completion notification from thesecurity provider device; and transmitting, by the least one processorof the computer-based system, a security provider task report.
 6. Themethod of claim 1, wherein the security task acceptance notificationincludes consumer data and provider data to enable communication betweenthe security provider device and the security consumer device.
 7. Asystem comprising: at least one processor; and a tangible,non-transitory memory configured to communicate with the at least oneprocessor, the tangible, non-transitory memory having instructionsstored thereon that, in response to execution by the at least oneprocessor, cause the at least one processor to perform operationscomprising: receiving a security task acceptance from a securityprovider device, the security task acceptance associated with a securitytask; validating the security task acceptance; and transmitting asecurity task acceptance notification in response to validating thesecurity task acceptance.
 8. The system of claim 7, wherein the securitytask acceptance includes a task identifier of the security task and aprovider identifier.
 9. The system of claim 7, wherein validating thesecurity task acceptance includes comparing a task time of the securitytask, a provider profile, and a task policy associated with the providerpolicy.
 10. The system of claim 7, wherein validating the security taskacceptance includes transmitting a plurality of security taskacceptances to the security consumer device and receiving selection ofone security task acceptance of the plurality of security taskacceptances from the security consumer device.
 11. The system of claim7, wherein the operations further comprise transmitting a security taskalert to the security provider device.
 12. The system of claim 7,wherein the operations further comprise receiving a security taskcompletion notification from the security provider device.
 13. Thesystem of claim 7, wherein the operations further comprise transmitting,by the least one processor of the computer-based system, a securityprovider task report including a provider identifier associated with thesecurity task acceptance.
 14. The system of claim 7, wherein theoperations further comprise: transmitting, by the least one processor ofthe computer-based system, a task activity to the security providerdevice, wherein in response to the security provider device detecting atask activity during the security task, the security provider device isconfigured to capture at least one of audio data, video data, andlocation information; receiving, by the least one processor of thecomputer-based system, the at least one of the audio data, the videodata, and the location information from the security provider device.15. An article of manufacture including a non-transitory, tangiblecomputer readable storage medium having instructions stored thereonthat, in response to execution by at least one processor, cause the atleast one processor to perform operations comprising: receiving asecurity task acceptance associated with a security task and a provideridentifier; validating the security task acceptance; and transmitting asecurity task acceptance notification in response to validating thesecurity task acceptance.
 16. The article of manufacture of claim 15,wherein validating the security task acceptance includes retrieving aprovider profile associated with the provider identifier, retrieving atask policy associated with the provider identifier, and comparing theprovider profile and the task policy.
 17. The article of manufacture ofclaim 15, wherein the operations further comprise providing videostreaming services to enable video to be streamed from the securityprovider device associated with the security task acceptance to asecurity consumer device associated with the security task.
 18. Thearticle of manufacture of claim 15, wherein the operations furthercomprise receiving provider data associated with the provider identifierand verifying the provider data.
 19. The article of manufacture of claim15, wherein the operations further comprise receiving a security taskcompletion notification and updating a provider profile associated withthe provider identifier in response to receiving the security taskcompletion notification.
 20. The article of manufacture of claim 15,wherein the operations further comprise generating a security providertask report including the provider identifier and a task time associatedwith the security task acceptance.